The table view displays information in a grid, where the rows are individual notes and the columns are Promoted Attributes. In addition, values are editable.

How it works

The tabular structure is represented as such:

There are also a few predefined columns:

Interaction

Creating a new table

Right click on an existing note in the Note Tree and select Insert child note and look for Table.

Adding columns

Each column is a promoted or unpromoted attribute that is defined on the Collection note.

To create a new column, either:

Adding new rows

Each row is actually a note that is a child of the Collection note.

To create a new note, either:

By default it will try to edit the title of the newly created note.

Alternatively, the note can be created from the Note Tree or scripting.

Context menu

There are multiple menus:

Editing data

Simply click on a cell within a row to change its value. The change will not only reflect in the table, but also as an attribute of the corresponding note.

Editing columns

It is possible to edit a column by right clicking it and selecting Edit column. This will basically change the label/relation definition at the collection level.

If the Name field of a column is changed, this will trigger a batch operation in which the corresponding label/relation will be renamed in all the children.

Working with the data

Sorting by column

By default, the order of the notes matches the order in the Note Tree. However, it is possible to sort the data by the values of a column:

Reordering and hiding columns

Reordering rows

Notes can be dragged around to change their order. To do so, move the mouse over the three vertical dots near the number row and drag the mouse to the desired position.

This will also change the order of the note in the Note Tree.

Reordering does have some limitations:

Nested trees

If the child notes of the collection also have their own child notes, then they will be displayed in a hierarchy.

Next to the title of each element there will be a button to expand or collapse. By default, all items are expanded.

Since nesting is not always desirable, it is possible to limit the nesting to a certain number of levels or even disable it completely. To do so, either:

Limitations:

Limitations

Use in search

The table view can be used in a Saved Search by adding the #viewType=table attribute.

Unlike when used in a Collection, saved searches are not limited to the sub-hierarchy of a note and allows for advanced queries thanks to the power of the Search.

However, there are also some limitations:

Columns are supported, by being defined as Promoted Attributes to the Saved Search note.

Editing is also supported.